Trigger on script completion

llandale - Mon May 09 15:33:38 EDT 2011
the current DXL context will wait for the eval_ to finish before continuing. Perhaps B can leave A a message in a file as to its status.

vasgyuszi - Mon May 09 17:25:26 EDT 2011
"the current DXL context will wait for the eval_ to finish before continuing. "

Obviously doesn't, because the next following infoBox after the eval_ line appears in the same time as the script B had start.

Meanwhile I have an idea:

1) Script B creates a formal module with a known name and to a known path (project root for example)
2) Script B closes it.
3) Script A sets a trigger to observe the creation event of this model with well known parameters
4) If the event happened, script A deletes the formal module in order to clean up
5) Script A continues its run

Could this work, what's your opinion?

Best regards,
vasgyuszi

Mathias Mamsch - Mon May 09 17:52:27 EDT 2011
Louie is right, eval_ WILL wait for the script to end before it continues. Remember that DOORS can only run one DXL at a time. So unless the eval_ code ends, no other DXL script will run. However if you start up a GUI with show or realize in eval, then the GUI will show up and the DXL will end and your calling script will continue after the eval. The GUI however will stay alive and be fed from DOORS from the GUI message loop.

Please don't implement a semaphore by creating a temporary module ;-) I am sure we can find a more elegant solution together. Do you want to elaborate on what you are trying to do?

Regards, Mathias

vasgyuszi - Tue May 10 00:24:23 EDT 2011
Thanks Mathias!

I'm sure, the introduced concept miss any elegancy, but could work.

You have right, the script B has its GUI starting with show and it appears also.
Why I thought eval_ don't wait: I got script B's GUI (waiting for usr inputs) and also got script A's infoBox placed after the eval_ line. I stopped here my activities for further investigation but today I'll try to let run script B with the appearing GUI.But I'll avoid to confuse the user by getting both GUIs at same time (one from script B and another from script A) beacuse the user could decide to click on A's GUI and mess up the execution sequence.

Thanks for Your advices!

Bestr regards,
vasgyuszi

vasgyuszi - Tue May 10 04:58:59 EDT 2011
Now I had experienced and let run the scripts:

1) A is running
2) A arrives the eval_ call of B
3) B 's GUI appears BUT A 's next line will be executed
4) Only A could continue because only *A*'s GUI is alive
5) After completion of A can be attached B 's GUI by the user .

This isn't what I want... I would suspend A 's execution until B ends.

What can I do?

Thanks alot,
vasgyuszi

Mathias Mamsch - Tue May 10 05:03:10 EDT 2011

The easiest way to do this would be, to replace show with block. Just run your script B using:
 

string sCode = "void show(DB x) { block x; release x; destroy x }
#include <...your b file...>"
eval_ sCode

This will make the GUI of B call block and therefore suspend A. Regards, Mathias

Mathias Mamsch, IT-QBase GmbH, Consultant for Requirement Engineering and D00RS

vasgyuszi - Tue May 10 08:39:45 EDT 2011
Thanks alot, Mathias!

It works perfectly, and last but not least: looks very elegant.

Best regards,
vasgyuszi

vasgyuszi - Mon May 09 17:25:26 EDT 2011
"the current DXL context will wait for the eval_ to finish before continuing. "

Obviously doesn't, because the next following infoBox after the eval_ line appears in the same time as the script B had start.

Meanwhile I have an idea:

1) Script B creates a formal module with a known name and to a known path (project root for example)
2) Script B closes it.
3) Script A sets a trigger to observe the creation event of this model with well known parameters
4) If the event happened, script A deletes the formal module in order to clean up
5) Script A continues its run

Could this work, what's your opinion?

Best regards,
vasgyuszi

vasgyuszi - Mon May 09 17:25:26 EDT 2011
"the current DXL context will wait for the eval_ to finish before continuing. "

Obviously doesn't, because the next following infoBox after the eval_ line appears in the same time as the script B had start.

Meanwhile I have an idea:

1) Script B creates a formal module with a known name and to a known path (project root for example)
2) Script B closes it.
3) Script A sets a trigger to observe the creation event of this model with well known parameters
4) If the event happened, script A deletes the formal module in order to clean up
5) Script A continues its run

Could this work, what's your opinion?

Best regards,
vasgyuszi

llandale - Tue May 10 10:15:33 EDT 2011

Here's something to play with. Change 'block' to 'show' and it behaves differently

string    DxlCode = 
"void clbk(DB db)
{  infoBox(\"Hellow from DxlCode clbk()\")
   return_(\"In clbk\")
}
DB db = create(\"Hello\")
apply(db, \"Say Hello\", clbk)
realize(db)
return_(\"Generated\")
infoBox(\"Before block\")
block(db)
destroy(db)
infoBox(\"after block\")
"  // end string DxlCode
string  Result  = eval_(DxlCode)
 
DB  db = create("Results")
DBE dbe = text(db, "", "Hello after eval_, code:\n" DxlCode "\nResult: " Result, 240, 250, true)
show(db)